Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!

Is there anything I can do to have this PR re-considered? I understand that adding a new feature, especially when its untested / untestable is a no go. What is the reason the current encrypted cast logic is commented out if I may ask? Is this something that is fixable? If so, I'm happy to take a look at it if would mean my PR could be re-considered.

I understand that Laravel receives a ton of PR requests, so there is no pressing urge to re-ignite this, but I though I would ask anyway. I really could use an encrypted version of the AsFluent class that is integrated into the framework codebase itself, as the modification in the HasAttributes trait is pretty essential for it to work properly.